Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

Remove the option during install to copy and customize all roles #76

Merged
merged 2 commits into from
May 12, 2020

Conversation

becw
Copy link
Member

@becw becw commented May 12, 2020

Only give the option to add an additional playbook. This won't break existing projects, since the variable that allows changing the provisioning source is still there.

…nly give the option to add an additional playbook. This won't break existing projects, since the variable that allows changing the provisioning source is still there.
@becw becw requested a review from byrond May 12, 2020 19:46
<property name="custom_playbook" value="${default.custom_playbook}" />
</else>
</if>
<input propertyName="custom_playbook" message="Add a custom Ansible playbook to your project " promptChar="?" validArgs="Y,n" defaultValue="${default.custom_playbook}" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always assume the default is in caps, so validArgs="y,N"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, never mind! I see that it's case sensitive. Oops!

Copy link
Contributor

@byrond byrond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this on a new project with and without a custom playbook, as well as a project with roles that were copied and customized (without reinstalling the-vagrant). Everything worked great! I ran the installer on the project with customized roles and saw the expected changes in the Vagrantfile. I assume it's up to the project's developer to revert any unwanted changes (for example, after installation, the customized playbook will not be run).

@becw becw merged commit a31aeb8 into develop May 12, 2020
@becw becw deleted the no-copy-provisioning branch May 12, 2020 20:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants